Precision
| Characteristic Name: | Precision |
| Dimension: | Accuracy |
| Description: | Attribute values should be accurate as per linguistics and granularity |
| Granularity: | Element |
| Implementation Type: | Rule-based approach |
| Characteristic Type: | Declarative |
Verification Metric:
| The number of tasks failed or under performed due to lack of data precision |
| The number of complaints received due to lack of data precision |
GuidelinesExamplesDefinitons
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Ensure the data values are correct to the right level of detail or granularity | (1) Price to the penny or weight to the nearest tenth of a gram. (2) precision of the values of an attribute according to some general-purpose IS-A ontology such as WordNet |
| Ensure that data is legitimate or valid according to some stable reference source like dictionary/thesaurus/code. | (1) Spellings and syntax of a description is correct as per the dictionary/thesaurus/Code (e.g. NYSIIS Code) (2) Address is consistent with global address book |
| Ensure that the user interfaces provide the precision required by the task | (1) if the domain is infinite (the rational numbers, for example), then no string format of finite length can represent all possible values. |
| Ensure the data values are lexically, syntactically and semantically correct | (1) “Germany is an African country” (semantically wrong); Book.title: ‘De la Mancha Don Quixote’ (syntactically wrong); UK’s Prime Minister: ‘Toni Blair’ (lexically wrong) |
Validation Metric:
| How mature is the creation and implementation of the DQ rules to maintain data precesion |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| if v = Jack,even if v = John, v is considered syntactically correct, as Jack is an admissible value in the domain of persons’ names | C. Batini and M, Scannapieco, “Data Quality: Concepts, Methodologies, and Techniques”, Springer, 2006. |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| Data values are correct to the right level of detail or granularity, such as price to the penny or weight to the nearest tenth of a gram. | ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing. |
| Data is correct if it conveys a lexically, syntactically and semantically correct statement – e.g.,the following pieces of information are not correct:“Germany is an African country” (semantically wrong);Book.title: ‘De la Mancha Don Quixote’ (syntactically wrong); UK’s Prime Minister: ‘Toni Blair’ (lexically wrong). | KIMBALL, R. & CASERTA, J. 2004. The data warehouse ETL toolkit: practical techniques for extracting. Cleaning, Conforming, and Delivering, Digitized Format, originally published. |
| The set S should be sufficiently precise to distinguish among elements in the domain that must be distinguished by users. This dimension makes clear why icons and colors are of limited use when domains are large. But problems can and do arise for the other formats as well, because many formats are not one-to-one functions. For example, if the domain is infinite (the rational numbers, for example), then no string format of finite length can represent all possible values. The trick is to provide the precision to meet user needs. | LOSHIN, D. 2001. Enterprise knowledge management: The data quality approach, Morgan Kaufmann Pub. |
| Is the information to the point, void of unnecessary elements? | LOSHIN, D. 2006. Monitoring Data quality Performance using Data Quality Metrics. Informatica Corporation. |
| The degree of precision of the presentation of an attribute’s value should reasonably match the degree of precision of the value being displayed. The user should be able to see any value the attributer may take and also be able to distinguish different values. | REDMAN, T. C. 1997. Data quality for the information age, Artech House, Inc. |
| The granularity or precision of the model or content values of an information object according to some general-purpose IS-A ontology such as WordNet. | STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733. |
Data volume
| Characteristic Name: | Data volume |
| Dimension: | Completeness |
| Description: | The volume of data is neither deficient nor overwhelming to perform an intended task |
| Granularity: | Information object |
| Implementation Type: | Process-based approach |
| Characteristic Type: | Usage |
Verification Metric:
| The number of tasks failed or under performed due to not meeting the right volume of data |
| The number of complaints received due to volume related issues |
GuidelinesExamplesDefinitons
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Define the scope of data in terms of organisational coverage to perform a business activity | (1) At least 70% of the production units should submit data to calculate total production efficiency of the company |
| Define the scope of data in terms of activities relates to any business task | (1) Pages with more than thousand hits per day and above are considered for the analysis |
| Define the scope of data in terms of the population of data which is under concern | (1) At least 10% of the population of white blood cells in the culture should be collected as samples to calculate its growth |
| Define an appropriate amount of records in terms of lower limit and upper limit for any task | (1) At least six responses should be available to evaluate a tutor's skills and competency. |
Validation Metric:
| How mature is the process of defining and maintaining appropriate data volumes of data |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| At the end of the first week of the Autumn term, data analysis was performed on the ‘First Emergency Contact Telephone Number’ data item in the Contact table. There are 300 students in the school and 294 out of a potential 300 records were populated, therefore 294/300 x 100 = 98% completeness has been achieved for this data item in the Contact table. | N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013. |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| A measure of the availability and comprehensiveness of data compared to the total data universe or population of interest. | D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008. |
| Is the scope of information adequate? (not too much nor too little). | EPPLER, M. J. 2006. Managing information quality: increasing the value of information in knowledge-intensive products and processes, Springer. |
| Degree of presence of data in a given collection. | SCANNAPIECO, M. & CATARCI, T. 2002. Data quality under a computer science perspective. Archivi & Computer, 2, 1-15. |
| The quantity or volume of available data is appropriate | WANG, R. Y. & STRONG, D. M. 1996. Beyond accuracy: What data quality means to data consumers. Journal of management information systems, 5-33. |